Systems and methods for conserving network resources

ABSTRACT

An account management engine for managing at least one prepaid wireless service account can include a calculation logic module that includes at least one scheduling algorithm configured to calculate a message delay time, the expiration of which triggers a continue message to be sent to a service switching point (SSP) instructing the SSP to continue an established call. A method for managing at least one prepaid service account can include calculating, based upon at least one scheduling algorithm, a message delay time, the expiration of which triggers a continue message to be sent to a service switching point (SSP) instructing the SSP to continue an established call.

TECHNICAL FIELD

The present disclosure relates generally to telecommunications services.More particularly, the present disclosure relates to systems and methodsfor conserving network resources.

BACKGROUND

Many wireless service providers offer wireless communication services,such as wireless voice service and wireless data service via prepaid andpostpaid service plans. Prepaid wireless services are popular amongcustomers who are ineligible for a postpaid service plan, such ascustomers with no or poor credit history and customers that do not wantthe obligation of a recurring bill. Prepaid customers can purchase voiceminutes, data throughput, and text messages at a set price via a varietyof methods, such as prepaid cards, Internet transactions, telephonetransactions, point-of-sale transactions, and in-call transactions, forexample. The prepaid customer can use the service until the purchaseminutes, data throughput, and/or messages are depleted, at which pointthe prepaid customer can replenish the account to continue using theservice.

Postpaid accounts are designed such that if the customer exceeds thenumber of voice minutes, data capacity, text messages, or otherservices, the postpaid customer will be charged for the excess serviceson a bill sent to the customer at the end of the billing cycle. Oftentimes, the customer is unaware of the overage and is requested to pay anunexpected bill at the end of the billing cycle. Services, such asAT&T's ROLLOVER® service aim to eliminate overages and accumulate unusedminutes for use in future billing cycles.

Prepaid wireless networks face the unique requirement of having toupdate prepaid accounts to reflect any service rendered in real-time ornear real-time. Methods have been developed to send messages to theserving mobile switching center (MSC) instructing the MSC to continue anestablished call every two minutes. A prepaid account balance isdecremented each time a message is sent. The message is sent withoutregard to the number of minutes available in the prepaid account,therefore all prepaid accounts will be updated via this method.

SUMMARY

According to one embodiment of the present disclosure, an accountmanagement engine for managing at least one prepaid wireless serviceaccount can include a calculation logic module that includes at leastone scheduling algorithm configured to calculate a message delay time.The expiration of the message delay time can trigger a continue messageto be sent to a service switching point (SSP) instructing the SSP tocontinue an established call.

In some embodiments the account management engine can further include anaccount balance database configured to store at least one accountbalance associated with at least one prepaid wireless service account.The account balance database can be further configured to update the atleast one account balance in response to the continue message beingsent.

In other embodiments the account management engine can further include arule database configured to store at least one rule used by the at leastone scheduling algorithm to calculate the message delay time. The atleast one rule can include at least one threshold account balance usedto trigger the calculation of a new message delay time. The at least onethreshold account balance can also trigger a warning tone. The at leastone threshold account balance can also trigger a replenish request. Thethreshold account balance can be a percentage of an account balance, amonetary value, a temporal value, or a data throughput value, forexample.

According to another embodiment of the present disclosure, a method formanaging at least one prepaid service account can include establishing acommunication session between a mobile device and a second device. Themethod can further include monitoring an account balance of a prepaidservice account associated with the mobile device to determine if athreshold account balance has been reached. If a threshold accountbalance has been reached, the method can proceed by continuing tomonitor the account balance of the prepaid service account. If athreshold account balance has not been reached, the method can proceedby calculating a message delay time and sending a continue message to anSSP according to the message delay time, and maintaining thecommunication session until the account balance is depleted. In someembodiments the second device is a wireline device and in otherembodiments the second device is a second mobile device. The thresholdaccount balance can be a percentage of the account balance, a monetaryvalue, a minute value, or a data throughput, for example.

According to yet another embodiment of the present disclosure, a methodfor managing at least one prepaid service account can includecalculating a message delay time based upon at least one schedulingalgorithm. The expiration of the message delay time can trigger acontinue message to be sent to an SSP instructing the SSP to continue anestablished call.

In some embodiments the method can further include updating, in responseto the continue message being sent, at least one account balance that isassociated with at least one prepaid wireless service account for whichthe call was established. The calculating step can be based upon atleast one rule used by the at least one scheduling algorithm tocalculate the message delay time. The at least one rule can include atleast one threshold account balance used to trigger the calculation of anew message delay time. The at least one threshold account balance canalso trigger a warning tone or a replenish request. The thresholdaccount balance can be a percentage of an account balance, a monetaryvalue, a minute value, or a data throughput value, for example.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 schematically illustrates a portion of an exemplarycommunications network in which some aspects of the present disclosurecan be practiced.

FIG. 2 schematically illustrates an exemplary account management engineand components thereof for use in accordance with an embodiment of thepresent disclosure.

FIG. 3 schematically illustrates a method for managing a prepaidaccount, according to an exemplary embodiment the present disclosure.

FIG. 4 is a message flow diagram illustrating a method for managing aprepaid account, according to an exemplary embodiment of the presentdisclosure.

DETAILED DESCRIPTION

As required, detailed embodiments of the present disclosure aredisclosed herein. It must be understood that the disclosed embodimentsare merely exemplary examples of the disclosure that may be embodied invarious and alternative forms, and combinations thereof. As used herein,the word “exemplary” is used expansively to refer to embodiments thatserve as an illustration, specimen, model or pattern. The figures arenot necessarily to scale and some features may be exaggerated orminimized to show details of particular components. In other instances,well-known components, systems, materials or methods have not beendescribed in detail in order to avoid obscuring the present disclosure.Therefore, specific structural and functional details disclosed hereinare not to be interpreted as limiting, but merely as a basis for theclaims and as a representative basis for teaching one skilled in the artto variously employ the present disclosure.

Referring now to the drawings wherein like numerals represent likeelements throughout the drawings, FIG. 1 illustrates a portion of anexemplary communications network 100, according to the presentdisclosure. The communications network 100 can include wirelessintelligent network (WIN) elements for facilitating intelligent networkfeatures and services including, but not limited to, a novel featureimplemented in accordance with the present disclosure to conservenetwork resources for wireless prepaid services by reducing messagessent to maintain an established communication session.

The communications network 100 can be configured as a 2G GSM (GlobalSystem for Mobile communications) network and can provide datacommunications via GPRS (General Packet Radio Service), and EDGE(Enhanced Data rates for GSM Evolution). The communications network 100can be configured as a 3G UMTS (Universal Mobile TelecommunicationsSystem) network and provide data communications via the HSPA (High-SpeedPacket Access) protocol family, such as, HSDPA (High-Speed DownlinkPacket Access), EUL (Enhanced Uplink) or otherwise termed HSUPA(High-Speed Uplink Packet Access), and HSPA+(Evolved HSPA). Thecommunications network 100 is also compatible with future mobilecommunications standards including, but not limited to, pre-4G and 4G,for example. Other technologies, such as, FDMA (Frequency DivisionMultiple Access), TDMA (Time Division Multiple Access), CDMA (CodeDivision Multiple Access), and the like are contemplated. The wirelesscommunications network 100 can be configured to provide messagingservices via SMS (Short Message Service), MMS (Multimedia MessageService), instant messaging, and USSD (Unstructured SupplementaryService Data, for example. The communications network 100 is describedbelow with reference to GSM terminology, however, in alternativeimplementations, the network components can be configured in accordancewith specifications of other technologies.

The illustrated communications network 100 has been simplified so as notto obscure the features of the present disclosure. Well-knowncomponents, systems, and/or methods have not been described in detail inorder to avoid obscuring the present disclosure. Additionally, someelements have been purposefully withheld from the illustratedcommunications network 100 and the description thereof for the sake ofbrevity and clarity of the disclosure. Other elements are illustrated assingle elements that can be representative of a plurality of likeelements.

It should be understood that features of the present disclosure can beimplemented in a network operated by one service provider or implementedamong one or more networks operated by one or more service providers.Further, features of the present disclosure are often described as beingimplemented to conserve network resources for pre-paid voice services.These features, however, can also be implemented to conserve networkresources for pre-paid data services or for other purposes. By way ofexample and to further contextualize the terms used in the followingdescription, a pre-paid service can use an account balance to serve asan actual or suggested limit on use of voice or data services. Anaccount balance can represent a time limit, such as time of use (e.g.,seconds, minutes, hours, days, etc.), a monetary limit, such as dollarsof use, or data throughput, such as bytes of use, for example. Theaccount balance can be established by prepayment or can berepresentative of an assigned limit on use, which the user may or maynot be allowed to exceed.

The illustrated communications network 100 includes a first mobiledevice 102 (hereinafter MD A 102) that is illustrated as being incommunication via an air interface with a base transceiver station (BTS)104 that, in turn, is illustrated as being in communication with a basestation controller (BSC) 106 via a communication link. MD A 102 can be amobile terminal, a user equipment, a computer, a handheld computer, aPDA, a smart phone, or other device capable of communication via acellular technology, such as one or more of the technologies describedabove, for example. Collectively, MD A 102, the BTS 104, and the BSC 106form a portion of a radio access network (RAN).

The BSC 106 is illustrated as being in communication with a mobileswitching center (MSC) 108 that serves to connect calls between variouspoints within the communications network 100. The MSC 108 operates asthe service switching point (SSP) in the WIN and can perform a serviceswitching function (SWF) in the WIN. The MSC 108 can include a visitinglocation register (VLR) 110. The VLR 110 can include all subscriber datarequired for call handling and mobility management for mobilesubscribers currently located in the area controller by the VLR 110. TheMSC 108 is illustrated as being in communication with the publicswitched telephone network (PSTN) 112 via a communications link. ThePSTN 112 can include a path to landline devices, such as acommunications device 114 that can be a landline telephone, for example.The PSTN 112 can also connect to the Internet (not shown), which canprovide packet-based communication, such as VoIP via a VoIP device. ThePSTN 112 can provide a path for communication between the MSC 108 andanother MSC 116. The MSC 116, like MSC 108, can include a VLR 118. TheMSC 116 is interconnected via a BSC 120 and a BTS 122 to a second mobiledevice 124 (hereinafter MD B 124).

The illustrated communications network 100 includes a signalingsubsystem that can be a signaling system number 7 (SS7) signalingsubsystem, for example. The core of the signaling subsystem can be asignal transfer point (STP) backbone network 126, illustrated as asingle STP. The STP backbone network 126 can include one or more STPsand associated signaling links. The STP backbone network 126 carriesout-of-band signals that are used to setup and tear down communicationsessions between MD A 102, MD B 124, and/or another communicationsdevice, such as the communications device 114 or a packet-basedcommunication device (not shown). The MSCs 108, 116 are each incommunication with the STP backbone network 126 via signaling links.

The illustrated STP backbone network 126 is in communication with acentralized service control point (SCP) 128 via a signaling link. TheSCP 128 can perform service control functions (SCF) in the WIN. The SCP128 can provide service control and service data functions, providemechanisms for introducing new services and customizing existingservices and features, and perform subscriber or application specificservice logic in response to a query from an MSC 108, 116 (SSP) andreply with instructions to perform specified functions and how tocontinue or terminate call processing. The illustrated SCP 128 includesan account management engine (AME) 130 in accordance with an embodimentof the present disclosure. The AME 130 can additionally or alternativelybe in communication with the SCP 128 or other network elements.

The AME 130 can be configured to calculate a message delay time. Themessage delay time can specify a time period, the expiration of whichtriggers the AME 130 to send a continue message to the serving MSC 108,116 to continue a call. The message time delay can be calculated for oneor more prepaid accounts associated with one or more subscribers. Theprepaid accounts can be associated with a voice service or a dataservice, for example. The AME 130 is described below in detail withreference to FIG. 2.

The illustrated SCP 128 is in communication with a number portabilitydatabase (NPDB) 132. The NPDB 132 can facilitate the scenario whereby asubscriber may retain their telephone number when moving to anotherlocation or to another carrier or operator. The NPDB 132 can return arouting number to the AME 130 to identify a called subscriber'ssubscription network for scenarios in which a calling subscriber roamsin the home public land mobile network (HPLMN) and the calledsubscriber's MSISDN indicates that the called subscriber subscribes to aPLMN within the calling subscriber's home country.

The illustrated STP backbone network 126 is in communication with a homelocation register (HLR) 134 via a signaling link. The HLR 134 servesstandard functions in the wireless network including providing routinginformation and maintaining subscription information. The HLR 134 can belocated in the SCP 128.

The illustrated STP backbone network 126 is also in communication withan intelligent peripheral (IP) 136 via a signaling path. The IP 136 canbe configured to perform specialized resource functions (SRF), such as,playing warning tones, playing announcements, collecting digits,providing speech recognition functions, and recording and storing voicemessages, for example. The IP 136 can be configured to send a warningtone to a prepaid subscriber's mobile device to warn the subscriber thata threshold account balance is near, has been reached, and/or has beenexceeded. A warning tone can be enabled/disabled based upon settings orpreferences of the service provider and/or the prepaid subscriber. TheIP 136 can further facilitate options to replenish a subscriber'sprepaid account.

Referring now to FIG. 2, an AME 130 and components thereof areillustrated, according to an exemplary embodiment of the presentdisclosure. The illustrated AME 130 includes a calculation logic module200. The calculation logic module 200 can include at least one processorand at least one computer-readable memory, wherein the at least onecomputer-readable memory is configured to store one or morecomputer-implemented scheduling algorithms 202 and the at least oneprocessor is configured to execute the one or more computer-implementedscheduling algorithms. In some embodiments the at least one processorand/or the at least one computer-readable memory can be configuredremote to the AME 130.

The illustrated AME 130 further includes a rules database 204 and anaccount balance database 206 that can be stored in a computer-readablememory of the calculation logic module 200 or another computer-readablememory of the AME 130. The rules database 204 can store at least onerule that can be used by the scheduling algorithm 202 to determine amessage delay time for a prepaid account. Rules can be applied to allprepaid accounts, a group of prepaid accounts, or individual prepaidaccounts. The rules database 204, the account balance database 206,and/or the scheduling algorithm 202 can include a list or otherindication of the rules to be applied to a particular prepaid account,group of prepaid accounts, or all prepaid accounts, for example.

The account balance database 206 can maintain account balances for oneor more prepaid service accounts associated with one or moresubscribers. An account balance can be updated at an interval specifiedby the message delay time. For example, if the calculation logic module200 calculates a message delay time of thirty minutes, the AME 130 cangenerate and send a continue message to the serving MSC 108, 116 everythirty minutes. The message can instruct the serving MSC 108, 116 tocontinue the call.

Embodiments of the present disclosure are described with particularreference to the Transactions Capability Part (TCAP) of the SignalingSystem Number 7 (SS7) protocol suite and Customized Applications forMobile network Enhanced Logic (CAMEL). Other protocols can be used toimplement the methods described herein including, but not limited to,Transfer Control Protocol/Internet Protocol (TCP/IP), Bearer IndependentCall Control (BICC), Session Initiation Protocol (SIP), Media GatewayControl Protocol (MGCP), H.323, variations, evolutions, and/orimprovements thereof, and other like protocols and technologies, forexample.

In current implementations used by many service providers, a continuemessage is sent every two minutes to maintain a call regardless of thenumber of minutes available in an account. By way of example, this twominute message delay time is referred to below as the typical messagedelay time. A warning tone is also typically applied when the accountbalance fails below one minute and the call is disconnected when theaccount balance is depleted.

The scheduling algorithm 202 can be used to determine the schedule bywhich continue messages are to be sent to the serving MSC 108, 116 basedupon the number of minutes remaining in an account balance. That is tosay, the scheduling algorithm 202 determines when to send a continuemessage and how long to allow a call to continue before sending asubsequent continue message.

The scheduling algorithm 202 can be a static algorithm that applies toall prepaid account balances based upon at least one static rule.Alternatively, the scheduling algorithm 202 can be a dynamic algorithmthat is designed to determine a message schedule based upon at least onerule. In the latter example, the scheduling algorithm 202 can includeone or more rules that apply to all account balances, wherein eachaccount balance can also include one or more additional rules. Forexample, a rule can be established to prevent the message delay timefrom being set to two minutes or any shorter time. This is merely anexample and the typical message delay time for other implementations maybe greater or less than two minutes. If any calculation of algorithm 202results in a message time delay that is a typical delay time or less,the algorithm 202 can continue in accordance with the previous messagingschedule and no changes will be made. A warning tone can be sent at anytime and/or a replenish request can be sent at any time per the serviceprovider's specifications, for example.

By way of example and not limitation, the scheduling algorithm 202 candetermine if an account balance is sufficient to continue a call for apercentage of the account balance and can determine a message delay timebased upon a percentage set in the rules database 204 for the prepaidaccount. Further, an account balance range can be defined in the rulesdatabase 204 for when a specific percentage is to be applied. Forexample, the scheduling algorithm 202 can use one percent of the accountbalance when the account balance is greater than or equal to one hundredminutes. When the account balance decreases to one hundred minutes orless, the rule can change to ten percent of the account balance and themessage delay time can be calculated accordingly. The account balancerange can define at least one threshold account balance that, whenreached or exceeded, triggers the scheduling algorithm to calculate anew message delay time based upon the percentage.

By way of another example and not limitation, the scheduling algorithm202 can calculate a best case scenario according to any rules applied bythe service provider. The service provider can establish a rule tomaximize the number of saved messages over the typical message delaytime. Alternatively, the service provider can establish a rule to reacha goal number of saved messages. As another alternative, the serviceprovider can establish a rule to save a minimum number of messages. Aservice provider can establish any rule or number of rules to achievewhat the service provider considers to be the best case scenario. Thenumber of saved messages can be calculated by using the calculatedmessage delay time divided by the typical message delay time. Forexample, assuming a typical message delay time of two minutes and acalculated message delay time of thirty minutes, the number of savedmessaged equals fifteen messages.

Generally, the scheduling algorithm 202 can be configured in accordancewith any specifications set forth by a wireless service provider, orpossibly a third party, to conserve network resources by reducing totalmessages sent to update a prepaid account.

Referring now to FIG. 3, a method 300 for managing a prepaid account isillustrated, according to an exemplary embodiment of the presentdisclosure. It should be understood that the steps of the process 300are not necessarily presented in any particular order and thatperformance of some or all the steps in an alternative order(s) ispossible and is contemplated. The steps have been presented in thedemonstrated order for ease of description and illustration. Steps canbe added, omitted and/or performed simultaneously without departing fromthe scope of the appended claims. It should also be understood that theillustrated process 300 can be ended at any time. Some or all steps ofthis process, and/or substantially equivalent steps, can be performed byexecution of computer-readable instructions stored on acomputer-readable memory in the form of a scheduling algorithm 202, forexample.

The method 300 begins and flow proceeds to block 302 wherein a call isestablished between two devices, at least one of which is a mobiledevice, for example, MD A 102 or MD B 124. The method 300 is describedwith reference to a call established between MD A 102 and MD B 124. Byway of example, a prepaid subscriber can originate a call from MD A 102by sending dialed digits to the MSC 108. The MSC 108 can receive thedialed digits and request instructions from the SCP 128 by sending acall setup request to the SCP 128 including the dialed digits and anidentifier of MD A 102. The AME 130 can identify the prepaidsubscriber's account based upon the identifier. The identifier can be anaccount number, a MSISDN, an IMSI, or other identifier capable of beinglinked to a prepaid account. The AME 130 can retrieve the initialaccount balance and flow can proceed to block 304, wherein the accountbalance is monitored in accordance with the scheduling algorithm 202 andrules 204 assigned for the prepaid account associated with MD A 102. Theaccount balance can be monitored such that if an account balancethreshold is reached or exceeded the scheduling algorithm 202 calculatesa new message delay time. If a threshold account balance is not reachedor exceeded, as determined in block 306, the method 300 can return toblock 304, wherein the account balance is monitored. If a thresholdaccount balance is reached or exceeded, the flow can proceed to block308 as explained immediately below.

At block 308, the scheduling algorithm 202 can be used to determine ifthe threshold is a warning threshold. A warning threshold is a thresholdaccount balance that can trigger the sending of a warning tone to MD A102. If it is determined that the threshold is not a warning threshold,flow proceeds to block 310, wherein the scheduling algorithm 202 cancalculate a new message delay time based upon the rules 204 assigned forthe account. A continue message can be generated and sent to the servingMSC 108 according to the calculated message delay time, as illustratedin block 312. The method 300 can return to block 304, wherein theaccount balance is monitored and continue messages are sent according tothe calculated message delay time until another threshold accountbalance is reached, as determined at block 306.

If it is determined, at block 308, that the threshold is a warningthreshold, flow proceeds to block 314, wherein a warning tone is sent toMD A 102. The SCP 128 can instruct the IP 136 to generate and send thewarning tone to MD A 102, for example. At block 316, it is determined ifa replenish request feature is enabled for the prepaid account. Areplenish request feature can function to provide the subscriber with anoption to replenish a prepaid account with funds to continue a call andcan be facilitated by the IP 136, for example.

If a replenish request feature is enabled for the prepaid account, flowcan proceed to block 318, wherein it is determined if a replenishrequest is received. If a replenish request is received, flow canproceed to block 320, wherein the account balance can be replenishedaccording to the replenish request. For example, the subscriber can addany number of minutes, data throughput, or monetary value to the prepaidaccount.

If a replenish request feature is not enabled, or if a replenish requestfeature is enabled but no replenish request is received, flow canproceed to block 322, wherein the call can continue until the accountbalance is depleted. Additional warning tones can be sent to MD A 102.At block 324, a disconnect message can be sent to the MSC 108 and thecall can be terminated at block 326. The method 300 can end.

Referring now to FIG. 4, a message flow diagram illustrating a method400 for managing a prepaid account is illustrated, according to anexemplary embodiment of the present disclosure. It should be understoodthat the steps of the process 400 are not necessarily presented in anyparticular order and that performance of some or all the steps in analternative order(s) is possible and is contemplated. The steps havebeen presented in the demonstrated order for ease of description andillustration. Steps can be added, omitted and/or performedsimultaneously without departing from the scope of the appended claims.It should also be understood that the illustrated process 400 can beended at any time. Some or all steps of this process, and/orsubstantially equivalent steps, can be performed by execution ofcomputer-readable instructions stored on a computer-readable memory, forexample, scheduling algorithm 202.

The method 400 is described with particular reference to a schedulingalgorithm 202 that employs three account balance thresholds, the last ofwhich is a warning threshold. As described above, the schedulingalgorithm 202 can be updated dynamically for each account, therefore,the method 400 can be modified with more or less account balancethresholds and may include more or less warning thresholds, replenishrequests, or other message delay time calculation than thoseillustrated.

As explained briefly above, the present disclosure can utilize variousprotocols including, but not limited to, TCAP, CAMEL, TCP/IP, BICC, SIP,MGCP, H.323, variations or improvements thereof, and other applicableprotocols or technologies, for example. The call control messages aredescribed below in generic terms, however, for purposes of explanationand not limitation, it is noted that the continue message, for example,can be a CAMEL application part (CAP) continue (CUE) message and theother messages can be part of the CAP protocol.

The method 400 can begin and MD A 102 can send a call setup request(cs_request) to the MSC 108 (step 402). The MSC 108 can receive thecs_request and forward the cs_request to the SCP 128 (step 404). The SCP128 can acknowledge the cs_request with an acknowledge message (cs_ack)(step 406) and can follow-up with a continue message (step 408) assumingthe subscriber's prepaid account has sufficient minutes to setup thecall. The call can be setup (step 410).

The call can continue and continue messages can be sent periodically inaccordance with the established message delay time until a thresholdaccount balance is detected and a new message delay time is calculated(step 412). A subsequent continue message can be sent (step 414) inaccordance with the new message delay time until the next thresholdaccount balance is detected and another new message delay time iscalculated (step 416). Another subsequent continue message can be sent(step 418) in accordance with the new message delay time until the nextthreshold account balance is detected and another new message delay timeis calculated (step 420). Steps 412-420 can be reiterated any number oftimes. For purposes of illustration, the threshold account balance instep 420 is illustrated as a warning threshold account balance.Accordingly, the SCP 128 can send a warning request (step 422) to the IP136. In response, the IP 136 can send a warning tone to the MD A 102(step 424) to notify the subscriber that the subscriber's accountbalance is low, for example. The account balance can be updated untilthe account balance is depleted at which point the SCP 128 can send adisconnect message (step 426) to a network element, for example, the MSC108, and the call can be terminated (step 428).

The aforementioned embodiments are described with respect to thereduction of messages on links carrying charging messages for prepaidwireless services. Aspects of the present disclosure, however, can beapplied to voice calls, data, text messaging, multimedia messaging,video messaging, and other telecommunications services offered bywireless, wireline, and/or converged wireless/wireline serviceproviders. Further, the present disclosure can be applied to thereduction of any other messages types, or for other purposes, forexample, power reduction, incentive programs, device-to-devicecommunications involved in debit or credit transactions, such as parkingmeters, toll roads/bridges, and vending machines, and other purposes.

It should also be understood that the present disclosure is not limitedto certain protocols and can be implemented using a variety of protocolsincluding those described herein, improvements, evolutions, orvariations thereof, and the like, for example.

The law does not require and it is economically prohibitive toillustrate and teach every possible embodiment of the present claims.Hence, the above-described embodiments are merely exemplaryillustrations of implementations set forth for a clear understanding ofthe principles of the disclosure. Variations, modifications, andcombinations may be made to the above-described embodiments withoutdeparting from the scope of the claims. All such variations,modifications, and combinations are included herein by the scope of thisdisclosure and the following claims.

What is claimed is:
 1. An account management engine, for managing aprepaid service account, comprising: a processor; and a memory havingcomputer-executable instructions that, when executed by the processor,cause the processor to perform operations comprising: calculating amessage delay time for a schedule according to whichcontinue-communication messages are transmitted to acommunications-network node for authorizing continuation of anestablished communication involving the prepaid service account; whereincalculating the message delay time comprises: calculating, by theprocessor, the message delay time according to a rule related to (i) abalance of the prepaid service account and (ii) a threshold accountbalance used to trigger calculation of the message delay time; andcalculating, by the processor, the message delay time, according to therule, in response to a determination that the balance of the prepaidservice account has a predetermined relationship to the thresholdaccount balance, wherein the processor calculates the delay time onlywhen triggered by the determination that the balance of the prepaidservice account has the predetermined relationship to the thresholdaccount balance.
 2. The account management engine of claim 1, whereinthe computer-executable instructions, when executed by the processor,cause the processor to perform the operations further comprisingcausing, in response to a continue-communication message being sent, anaccount balance database to update the prepaid service account balancestored at the database.
 3. The account management engine of claim 1,wherein the threshold account balance is a predetermined percentage ofthe balance of the prepaid service account.
 4. The account managementengine of claim 1, wherein the rule prevents the processor from puttinginto effect any message delay time calculated to be below apredetermined value.
 5. The account management engine of claim 4,wherein the rule causes the processor to, in response to a determinationthat a calculation would result in a new message delay time being belowthe predetermined value, determine not to put the new message delay timeinto effect.
 6. The account management engine of claim 1, wherein therule causes the processor to calculate the message delay time using apercentage of the balance of the prepaid service account.
 7. The accountmanagement engine of claim 1, wherein the rule describes: an accountbalance range; a first percentage for use to calculate the message delaytime when the balance of the prepaid service account is within theaccount balance range; and a second percentage for use to calculate themessage delay time when the balance of prepaid service account isoutside of the account balance range.
 8. The account management engineof claim 1, wherein the rule describes: a first percentage for use tocalculate the message delay time when the balance of the prepaid serviceaccount is greater than or equal to a particular value; and a secondpercentage for use to calculate the message delay time when the balanceof the prepaid service account is below the particular value.
 9. Theaccount management engine of claim 8, wherein: the particular value is afirst particular value; and the rule describes a third percentage foruse, to calculate the message delay time when the balance of the prepaidservice account is greater than or equal to a second particular value.10. The account management engine of claim 1, wherein the balance of theprepaid service account has the predetermined relationship to thethreshold balance when the balance of the prepaid service account isless than the threshold balance.
 11. A method, for managing a prepaidservice account, comprising: calculating, by a calculation logic modulehaving a processor, a message delay time for a schedule according towhich continue-communication messages are transmitted to acommunications-network node for authorizing continuation of anestablished communication involving the prepaid service account; whereincalculating the message delay time includes calculating the messagedelay time according to a rule related to (i) a balance of the prepaidservice account and (ii) a threshold account balance used to triggercalculation of the message delay time; and wherein calculating themessage delay time is triggered, according to the rule, in response to adetermination that the balance of the prepaid service account has apredetermined relationship to the threshold account balance, and thecalculation logic module calculates the message delay time only whentriggered by the determination that the balance of the prepaid serviceaccount has the predetermined relationship to the threshold accountbalance.
 12. The method of claim 11, wherein the threshold accountbalance is a predetermined percentage of the balance of the prepaidservice account.
 13. The method of claim 11, wherein the rule preventsthe calculation logic module from putting into effect any message delaytime calculated to be below a predetermined value.
 14. The method ofclaim 11, wherein the rule causes the calculation logic module tocalculate the message delay time using a percentage of the balance ofthe prepaid service account.
 15. The method of claim 11, wherein therule describes: an account balance range; a first percentage for use bythe calculation logic module, to calculate the message delay time, whenthe balance of the prepaid service account is within the account balancerange; and a second percentage for use by the calculation logic module,to calculate the message delay time, when the balance of prepaid serviceaccount is outside of the account balance range.
 16. The method of claim11, wherein the rule describes: a first percentage for use by thecalculation logic module, to calculate the message delay time, when thebalance of the prepaid service account is greater than or equal to aparticular value; and a second percentage for use by the calculationlogic module, to calculate the message delay time, when the balance ofthe prepaid service account is below the particular value.
 17. Themethod of claim 11, wherein the balance of the prepaid service accounthas the predetermined relationship to the threshold balance when thebalance of the prepaid service account is less than the thresholdbalance.
 18. A computer-readable storage device comprisingcomputer-executable instructions that, when executed by a processor,cause the processor to perform operations, for managing a prepaidservice account, comprising: calculating a message delay time for aschedule according to which continue-communication messages aretransmitted to a communications-network node for authorizingcontinuation of an established communication involving the prepaidservice account; wherein calculating the message delay time includescalculating the message delay time according to a rule related to (i) abalance of the prepaid service account and (ii) a threshold accountbalance used to trigger the calculation of the message delay time; andwherein calculating the message delay time is triggered, according tothe rule, in response to a determination that the balance of the prepaidservice account has a predetermined relationship to the thresholdaccount balance, and the processor calculates the message delay timeonly when triggered by the determination that the balance of the prepaidservice account has the predetermined relationship to the thresholdaccount balance.
 19. The computer-readable storage device of claim 18,wherein the threshold account balance is a predetermined percentage ofthe balance of the prepaid service account.
 20. The computer-readablestorage device of claim 18, wherein the balance of the prepaid serviceaccount has the predetermined relationship to the threshold balance whenthe balance of the prepaid service account is less than the thresholdbalance.